Description

The refactoring introduced in #21139 around type handling broke the implementation of the hasComplexVars helper function used in the model template. This PR removes Date.t, DateTime.t, from the list of primitive types to re-introduce the old behavior.

I believe that Date.t and DateTime.t should be considered primitive types, but that would require significant changes to the implementation of the hasComplexVars helper function or the model.mustache template. I suggest parking this discussion and see how #21208 progresses, since it may introduce a full revamp of how the Elixir generator works with models.

This PR should unblock the work being done in #21214.

@wing328, I decided to strip this out from #21215 because the change affects the Elixir generator and not just the tests. If you think this should be approached differently, the commit can be easily cherry-picked.

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in Git BASH)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.